Node / meshtastic / Meshtastic-Android / files / docs / roadmap.md

Displaying Rendered • View raw • Download

│ Last updated: 2026-03-31

Forward-looking priorities for the Meshtastic KMP multi-target effort. For current state, see kmp-status.md. For the full gap analysis, see decisions/architecture-review-2026-03.md.

These items address structural gaps identified in the March 2026 architecture review. They are prerequisites for safe multi-target expansion.

Objective: Complete desktop wiring for all features and ensure full integration.

• ✅ Settings: ~35 screens with real configuration, including theme/about parity and desktop language picker support

• ✅ Nodes: Adaptive list-detail with node management

• ✅ Messaging: Adaptive contacts with message view + send

• ✅ Connections: Dynamic discovery of platform-supported transports (TCP, Serial/USB, BLE)

• ❌ Map: Placeholder only, needs MapLibre or alternative

• ⚠️ Firmware: Fully KMP (Unified OTA + native Secure DFU + USB/UF2); desktop is first-class target

• ⚠️ Intro: Onboarding flow (may not apply to desktop)

1. Tier 1: Core Wiring (Essential)

• Complete Map integration (MapLibre or equivalent)

• Verify all features accessible via navigation

• Test navigation flows end-to-end

2. Tier 2: Polish (High Priority)

• Additional desktop-specific settings polish

• ✅ Keyboard shortcuts via T383838onPreviewKeyEvent (MenuBar removed)

• Adaptive density & multitasking optimizations (2026 Desktop Guidelines)

• Window management

• State persistence

3. Tier 3: Advanced (Nice-to-have)

• Performance optimization

• Advanced map features

• Theme customization

• Multi-window support

1. Evaluate KMP-native testing tools — ✅ Done: Fully evaluated and integrated T383838Mokkery, T383838Turbine, and T383838Kotest across the KMP modules. T383838mockk has been successfully replaced, enabling property-based and Flow testing in T383838commonTest for iOS readiness.

2. Desktop Map Integration — Address the major Desktop feature gap by implementing a raster map view using **MapComposeMP**.

• Implement a T383838MapComposeProvider for Desktop.

• Implement a Web Mercator Projection helper in T383838feature:map/commonMain to translate GPS coordinates to the 2D image plane.

• Leverage the existing T383838BaseMapViewModel contract.

3. Unify T383838MapViewModel — Collapse the remaining Google and F-Droid specific T383838MapViewModel classes in the T383838:app module into a single T383838commonMain implementation by isolating platform-specific settings (styles, tile sources) behind a repository interface.

4. iOS CI gate — ✅ Done: added T383838iosArm64()/T383838iosSimulatorArm64() to convention plugins and CI. T383838commonMain successfully compiles on iOS.

1. iOS proof target — ✅ Done (Stubbing): Stubbed iOS target implementations (T383838NoopStubs.kt equivalent) to successfully pass compile-time checks. Next: Setup an Xcode skeleton project and launch the iOS app.

2. Migrate to Navigation 3 Scene-based architecture — leverage the first stable release of Nav 3 to support multi-pane layouts. Investigate 3-pane "Power User" scenes (e.g., Node List + Detail + Map/Charts) on Large (1200dp) and Extra-large (1600dp) displays (Android 16 QPR3).

3. T383838core:api contract split — separate transport-neutral service contracts from the Android AIDL packaging to support iOS/Desktop service layers.

1. Platform-Native UI Interop —

• iOS Maps & Camera: Implement T383838MapLibre or T383838MKMapView via Compose Multiplatform's T383838UIKitView. Leverage T383838AVCaptureSession wrapped in T383838UIKitView to fulfill the T383838LocalBarcodeScannerProvider contract.

• Web (wasmJs) Integrations: Leverage T383838HtmlView to embed raw DOM elements (e.g., T383838<video>, T383838<iframe>, or canvas-based maps) directly into the Compose UI tree while binding the root app via T383838CanvasBasedWindow.

2. Module maturity dashboard — living inventory of per-module KMP readiness.

3. Shared UI vs Shared Logic split — If the iOS target utilizes native SwiftUI instead of Compose Multiplatform, evaluate splitting feature modules into pure T383838sharedLogic (business rules, ViewModels) and T383838sharedUI (Compose Multiplatform) to prevent dragging Compose dependencies into pure native iOS apps.

1. Solve in T383838commonMain first. If it doesn't need platform APIs, it belongs in T383838commonMain.

2. Interfaces in T383838commonMain, implementations per-target. The repository pattern is established — extend it. Prefer dependency injection (Koin) with interfaces over T383838expect/T383838actual declarations whenever possible to keep architecture decoupled and highly testable.

3. UI Interop Strategies. When a Compose Multiplatform equivalent doesn't exist (e.g., Maps, Camera), use standard interop APIs rather than extracting the entire screen to native code. Use T383838AndroidView for Android, T383838UIKitView for iOS, T383838SwingPanel for JVM/Desktop, and T383838HtmlView for Web (T383838wasmJs). Always wrap these in a shared T383838commonMain interface contract (like T383838LocalBarcodeScannerProvider).

4. Stubs are a valid first implementation. Every target starts with no-op stubs, then graduates to real implementations.

5. Feature modules stay target-agnostic in T383838commonMain. Platform UI goes in platform source sets. Keep the UI layer dumb and rely on shared ViewModels (Unidirectional Data Flow) to drive state.

6. Transport is a pluggable adapter. BLE, serial, TCP, MQTT all implement T383838RadioTransport and are orchestrated by a shared T383838RadioInterfaceService.

7. CI validates every target. If a module declares T383838jvm(), CI compiles it. No exceptions. Run tests on appropriate host runners (macOS for iOS, Linux for JVM/Android) to catch platform regressions.

8. Test in T383838commonTest first. ViewModel and business logic tests belong in T383838commonTest so every target runs them. Use shared T383838core:testing utilities to minimize duplication.

9. Zero Platform Leaks. Never import T383838java.* or T383838android.* inside T383838commonMain. Use KMP-native alternatives like T383838kotlinx-datetime and T383838Okio.